-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libethdrivers: make zynqmp driver usable #161
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me.
@axel-h Long story short, a lot of our customers require us to OPSEC each commit we want to open-source, which takes a long time. The two commits we released were ones we had approval for, and we've been using the zynqmp ethdrivers way before the driver framework was released. The goal was to have another series of commits made available that make the zynqmp usable, with an example platform, but the OPSEC process is taking a lot longer than anticipated |
80a4f3e
to
bd69576
Compare
b2c7174
to
5cbedc7
Compare
Can we merge this or is something blocking this still? |
Co-authored-by: Sebastian Eckl <sebastian.eckl@hensoldt.net> Signed-off-by: Axel Heider <axel.heider@hensoldt.net>
Co-authored-by: Sebastian Eckl <sebastian.eckl@hensoldt.net> Signed-off-by: Axel Heider <axel.heider@hensoldt.net>
@chrisguikema I'm a bit confused actually, how do things work for you without these changes?